Thanks @aatanasov-cloudinary ! It turns out, the container elements used a slight different syntax for its keys (heading and such use _background_image while the container types use background_image).

Furthermore, the container applies an extra suffix internally which I couldn't retrieve directly via Elementor's internals, so I've applied it directly in that case. This fixes the issue now.

I've also added some extra defensive code to check all Elementor methods interactions, as we can't be certain these methods will still exist in future versions.
Another option would be to use

try {
 // internal method calls.
}
catch ( \Throwable $e ) {
}

however Throwable isn't available in PHP 5.6 so perhaps this would be a good future improvement once we drop PHP 5.6 support.

Anyway, have a look and let me know your thoughts!

@gabriel-detassigny, thanks, when adding a background image to a container, I can see we have the following in the CSS:

Can you please check if we can optimize this as well (both selectors use background images delivered by Cloudinary)?

Also, it will be helpful to look into the background overlay case. It uses ::before:

Front-end

CMS

Thanks @aatanasov-cloudinary
For extra context: the rule you found with the URL still set as the local one was actually the remaining default Elementor one. When we add our own rules, they either:

• replace the existing one if they exactly match the same selector
• get added as a new CSS rule

So I've made changes to try to ensure we replace the existing rules (including the overlay which I've added support for). It's not an easy job though as Elementor checks for a lot of pseudo-elements, child elements, etc. And we can't guarantee this won't change in a future version.

Still, it seems to work well right now, so have a look and let me know!